Skip to content

doc/uefi: improve Protocol documentation #1612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Conversation

phip1611
Copy link
Member

@phip1611 phip1611 commented Apr 7, 2025

Improve Protocol documentation in general. The idea here is to centralize all documentation in uefi-raw and then forward to it from UEFI.

Partially covers #1639

Checklist

  • Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
  • Update the changelog (if necessary)

@phip1611 phip1611 requested a review from nicholasbishop April 7, 2025 12:51
@phip1611 phip1611 self-assigned this Apr 7, 2025
@phip1611

This comment was marked as outdated.

@phip1611 phip1611 mentioned this pull request Apr 7, 2025
15 tasks
@seijikun

This comment was marked as outdated.

@phip1611 phip1611 removed the request for review from nicholasbishop April 7, 2025 15:21
@phip1611 phip1611 marked this pull request as draft April 7, 2025 15:21
@phip1611 phip1611 marked this pull request as ready for review April 8, 2025 07:30
@phip1611 phip1611 changed the title doc/uefi: improve device path documentation doc/uefi: improve Protocol and Device Path documentation Apr 8, 2025
@phip1611 phip1611 requested a review from nicholasbishop April 8, 2025 07:30
@phip1611 phip1611 force-pushed the doc-devicepath branch 2 times, most recently from 3213ebd to 999927a Compare April 8, 2025 07:34
//! another.
//!
//! Implementation-wise, a protocol is a `C` struct holding function pointers
//! and/or data. Please note that some protocols may use [`core::ptr::null`] as
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nicholasbishop I'd like to add more about protocol interfaces being null; why can they be null and when is this valid? Can you help?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's the issue where it was first brought to our attention that the interface could be null: #859

So LoadedImageDevicePath on an image created with a null device path is one way, but probably not the only way to end up with a null interface.

@phip1611 phip1611 changed the title doc/uefi: improve Protocol and Device Path documentation doc/uefi: improve Protocol documentation Apr 19, 2025
The idea is that people should not always read the uefi-raw doc
in any case. Therefore, a briefly simplified version of the uefi-raw
doc is now also in uefi.

See #1641 (comment)
for a discussion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants